Skip to content

docs: add cargo-axi to community catalog - #114

Closed
AG9898 wants to merge 2 commits into
kunchenguid:mainfrom
AG9898:agent/add-cargo-axi-catalog
Closed

docs: add cargo-axi to community catalog#114
AG9898 wants to merge 2 commits into
kunchenguid:mainfrom
AG9898:agent/add-cargo-axi-catalog

Conversation

@AG9898

@AG9898 AG9898 commented Jul 24, 2026

Copy link
Copy Markdown

What Changed

  • Added a cargo-axi entry (Rust / Cargo, author AG9898) to catalog.yaml as the single source for the community catalog.
  • Regenerated the catalog regions in README.md and docs/index.html so the rendered community table includes the new cargo-axi row.

Risk Assessment

✅ Low: A documentation-only community catalog addition whose entry is consistent across the catalog.yaml source and both generated README/docs regions, with no code, behavior, or invariant changes.

Testing

Ran the targeted docs-generation checks (docs:check and docs:test), both green, confirming the cargo-axi entry in catalog.yaml is consistently reflected in the generated README.md and docs/index.html regions with no drift. Then captured reviewer-visible visual evidence by rendering the docs site in a browser and screenshotting the community catalog table, which shows the new cargo-axi row (author AG9898, domain Rust / Cargo, with the check/Clippy TOON description). Overall result: the catalog addition works as intended end-to-end.

  • Evidence: Rendered docs community catalog showing cargo-axi row (local file: /tmp/no-mistakes-evidence/01KYB2E8SYN15TVEB9WBQCZ8GV/cargo-axi-catalog.png)
Evidence: docs:check drift verification
$ node scripts/generate-docs.mjs --check
docs:check ok — generated regions match their sources

Pipeline

Updates from git push no-mistakes

⏭️ **intent** - skipped

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

  • corepack pnpm run docs:check — generated regions match catalog.yaml (no drift)
  • corepack pnpm run docs:test — 4/4 catalog rendering tests pass
  • Served docs/ over HTTP and rendered docs/index.html in a browser, then captured a screenshot of the community catalog table showing the cargo-axi row (AG9898 / Rust / Cargo)
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

@kunchenguid kunchenguid left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Speaking as Kun's firstmate: catalog-only diff, no security issue. Independent source review at ca4b3d9 admits cargo-axi.

@kunchenguid

Copy link
Copy Markdown
Owner

Speaking as Kun's firstmate: I reviewed the diff (catalog.yaml plus generated README.md / docs/index.html only) and independently inspected the package.

Independent source review at pin ca4b3d9cabc7938fd478dd92ffb1940ee3f1c70b (tag v0.1.0, also current main HEAD). Files read: src/main.rs, src/cli.rs, src/lib.rs, src/output.rs, src/hooks.rs, plus the recursive tree at that revision. Direct observations at that revision:

  • TOON via toon_format::encode_default at the output boundary only (src/output.rs)
  • cargo axi no-args home prints bin, description, workspace summary, and a compact default-member package list with a hint to list all
  • packages defaults to 3 fields (name, version, targets) with --limit (default 100) and --full; total is always included
  • unknown flags rejected per command with valid flags listed; structured {error, help} on stdout; exit 0/1/2
  • principle 7 held: cargo axi setup hooks <install|inspect|remove> --app claude|codex|opencode|all merges/repairs JSON hooks (does not overwrite unmanaged files), PATH-vs-absolute executable, session start/end
  • generated skills/cargo-axi/SKILL.md is checked against CLI metadata
  • principle 10 --version / -v / -V not held (treated as unknown command). Help pages and home identification otherwise hold. Same class of gap docs: propose forgejo-axi for the community catalog #150 treated as partial, not the blocker.

VISION.md per-rule:

  • AXI principles: aligns for admission at this pin (principle 7 held; --version noted as a remaining P10 gap, not blocking).
  • Catalog: aligns. Inspected source at ca4b3d9 satisfies applicable AXI principles for a community catalog add. Description matches the inspected surface.
  • SDKs: aligns (docs-only catalog add; no SDK change).

I resolved the catalog conflict file-only (catalog.yaml + docs:gen) and pushed to the contributor fork. Admitting and merging if CI is green.

@kunchenguid

Copy link
Copy Markdown
Owner

Speaking as Kun's firstmate.

This catalog entry landed via last-resort port #156 (squash merge 910c24b9cad070cf7fe80e54c3634a80d7537fad) because #114 stayed CONFLICTING on the fork after a file-only resolve + docs:gen push. No rebase was requested. Closing this original as redundant now that cargo-axi is on main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants